[No QA] Helpsite consolidateV2 #81045

stephanieelliott · 2026-01-30T18:22:09Z

Explanation of Change

Fixed Issues

$
PROPOSAL:

Tests

Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

Verify that no errors appear in the JS console

PR Author Checklist

I linked the correct issue in the ### Fixed Issues section above
I wrote clear testing steps that cover the changes made in this PR
- I added steps for local testing in the Tests section
- I added steps for the expected offline behavior in the Offline steps section
- I added steps for Staging and/or Production testing in the QA steps section
- I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
- I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
I included screenshots or videos for tests on all platforms
I ran the tests on all platforms & verified they passed on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
I verified there are no new alerts related to the canBeMissing param for useOnyx
I followed proper code patterns (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
  - If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I followed the guidelines as stated in the Review Guidelines
I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
I verified that if a function's arguments changed that all usages have also been updated correctly
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
If new assets were added or existing ones were modified, I verified that:
- The assets are optimized and compressed (for SVG files, run npm run compress-svg)
- The assets load correctly across all supported platforms.
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

melvin-bot · 2026-01-30T18:22:47Z

melvin-bot · 2026-01-30T18:22:50Z

@rlinoz @greg-schroeder One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

github-actions · 2026-01-30T18:23:58Z

docs/articles/consolidated/billing/manage-your-billing.md

@@ -0,0 +1,5 @@
+—


YAML frontmatter syntax error: The YAML frontmatter delimiters should use three hyphens --- (not em dashes —).

This will prevent the YAML metadata from being parsed correctly. Change to:

--- title: Manage Your Billing ---

github-actions · 2026-01-30T18:23:59Z

docs/articles/consolidated/billing/manage-your-billing.md

@@ -0,0 +1,5 @@
+—
+title: Manage Your Billing


Missing YAML metadata (AI Readiness violation): The frontmatter is missing required fields for AI readiness:

description: A concise, benefit-focused summary

keywords: Feature name, related terms, navigation path, etc.

Example:

--- title: Manage Your Billing description: Learn how to view and manage your Expensify billing and subscription details. keywords: [billing, subscription, payment, invoice, manage billing, billing settings] ---

github-actions · 2026-01-30T18:24:00Z

docs/articles/consolidated/billing/manage-your-billing.md

+title: Manage Your Billing
+—
+
+Article body here.


Placeholder content (Readability violation): The article contains only placeholder text "Article body here." This provides no useful information to users.

Please add complete, informative content that:

Uses clear, scannable headings

Provides step-by-step instructions where applicable

Uses 8th grade reading level or below

Includes a breadcrumb path below the H1 heading

github-actions · 2026-01-30T18:25:34Z

HelpDot Documentation Review

Overall Assessment

This PR introduces a new consolidated platform section to the HelpDot documentation structure, but the implementation is incomplete and contains several critical issues that must be addressed before merging.

Scores Summary

Readability: 1/10 - Placeholder text only with YAML syntax error
AI Readiness: 2/10 - No metadata, broken YAML formatting
Style Compliance: 1/10 - Multiple violations including YAML syntax, missing metadata, placeholder content

Key Findings - Critical Issues

Broken YAML: Uses em-dash instead of triple-dash delimiters
Placeholder Content: Only Article body here - no actual documentation
Missing Metadata: No description, keywords, or internalScope
Wrong URL: Uses travel.expensify.com instead of proper consolidated domain
Capitalization Issues: Lowercase titles throughout routing config

Recommendations Priority 1 - Blocking

Fix YAML syntax error
Add complete article content
Add required frontmatter fields
Fix routing configuration URL and capitalization
Clarify what consolidated platform represents

Files Reviewed

docs/_data/_routes.yml: Structural issues with URL, capitalization
docs/articles/consolidated/billing/manage-your-billing.md: Critical YAML error, no content
docs/consolidated/hubs/billing/index.html: Title inconsistencies
docs/consolidated/hubs/index.html: Template title mismatch

Final Recommendation

Do not merge until Priority 1 blocking issues resolved. This would break builds and provide no user value.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 86c7ce2825

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector · 2026-01-30T18:27:33Z

docs/articles/consolidated/billing/manage-your-billing.md

+—
+title: Manage Your Billing
+—


Use valid YAML front matter delimiters

The page front matter uses Unicode em dashes (—) instead of the required --- delimiters, so Jekyll will not treat this as a Markdown page with metadata. In that case the file is copied as a static asset and the title is ignored, which means the article won’t render through the site layout and will show the raw front matter line. This will happen whenever the docs site is built by Jekyll.

Useful? React with 👍 / 👎.

OSBotify · 2026-01-30T18:57:31Z

A preview of your ExpensifyHelp changes have been deployed to https://fa1c25f9.helpdot.pages.dev ⚡️

Updated articles:

…ocs/articles/consolidated/billing/Subscription and Plan Management/How-billing-ownership-and-subscription-management-work-in-Expensify.md

…iptions-in-Expensify.md

… How-to-Manage-Subscriptions-and-Billing-in-New-Expensify.md

…s-in-Expensify.md

…rectory

codecov · 2026-01-30T22:44:59Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
see 106 files with indirect coverage changes

…ement/index.html

…wnership-means-in-expensify.md

…pdate corresponding HTML file

…ctions

…reflect the changes

…yml and create corresponding markdown files

stephanieelliott added 4 commits January 30, 2026 08:11

Update _routes.yml

8098318

Create index.html

08e731e

Create index.html

0a136bd

Create manage-your-billing.md

86c7ce2

stephanieelliott requested a review from a team as a code owner January 30, 2026 18:22

melvin-bot bot assigned stephanieelliott Jan 30, 2026

melvin-bot bot requested review from greg-schroeder and rlinoz and removed request for a team January 30, 2026 18:22

github-actions bot reviewed Jan 30, 2026

View reviewed changes

chatgpt-codex-connector bot reviewed Jan 30, 2026

View reviewed changes

stephanieelliott added 5 commits January 30, 2026 08:33

Update _routes.yml

0d0b14e

Update hub.html

a91dd2c

Update manage-your-billing.md

59b3ad9

Update hub.html

5b22008

Update lhn-template.html

91097cf

github-actions bot changed the title ~~Helpsite consolidayev2~~ [No QA] Helpsite consolidayev2 Jan 30, 2026

stephanieelliott changed the title ~~[No QA] Helpsite consolidayev2~~ [No QA] Helpsite consolidateV2 Jan 30, 2026

stephanieelliott added 3 commits January 30, 2026 10:31

Update manage-your-billing.md

ce3fb89

Create Manage-Billing-and-Subscriptions-in-New-Expensify.md

41eb283

Create Manage-Billing-and-Subscriptions-in-Expensify-Classic.md

a248bee

stephanieelliott removed request for greg-schroeder and rlinoz January 30, 2026 20:38

Rename docs/articles/consolidated/billing/manage-your-billing.md to d…

039a5d4

…ocs/articles/consolidated/billing/Subscription and Plan Management/How-billing-ownership-and-subscription-management-work-in-Expensify.md

stephanieelliott added 17 commits January 30, 2026 11:03

Create What-billing-ownership-means-in-Expensify.md

35f112a

Update What-billing-ownership-means-in-Expensify.md

bb703ab

Create How-to-manage-subscriptions-in-Expensify.md

02b4c68

Create How-to-manage-subscriptions-and-billing-in-New-Expensify.md

a46d4d5

Create Deleting-workspaces-in-Expensify.md

1e9c192

Rename How-to-manage-subscriptions-in-Expensify.md to Managing-subscr…

0cb6a6a

…iptions-in-Expensify.md

Update Managing-subscriptions-in-Expensify.md

166fa65

Create How-to-Manage-Billing-and-Subscriptions-in-Expensify-Classic.md

beeec54

Rename How-to-manage-subscriptions-and-billing-in-New-Expensify.md to…

1d3a915

… How-to-Manage-Subscriptions-and-Billing-in-New-Expensify.md

Create What-billing-ownership-means-in-Expensify.md

2b8d583

Update createDocsRoutes.ts

be03086

Create index.html

1911bac

Create What-billing-ownership-means-in-Expensify.md

0488e60

Update _routes.yml

b29378a

Delete docs/articles/consolidated/billing/What-billing-ownership-mean…

ee1a800

…s-in-Expensify.md

Delete docs/articles/consolidated/Subscription and Plan Management di…

fc8deab

…rectory

Update _routes.yml

0adfb9b

stephanieelliott and others added 12 commits January 30, 2026 12:50

Update createDocsRoutes.ts

3b1379e

Update _routes.yml

e5c3d3d

Update _routes.yml

6c588ac

Delete docs/articles/consolidated/billing/subscription-and-plan-manag…

d85bd30

…ement/index.html

Rename What-billing-ownership-means-in-Expensify.md to what-billing-o…

d9339f3

…wnership-means-in-expensify.md

Add subscription and plan management section to billing in _routes.yml

75daa0a

Refactor billing section titles and descriptions in _routes.yml and u…

695f216

…pdate corresponding HTML file

Add new articles on subscription and workspace management to _routes.yml

93347bd

Add new billing-related HTML files for setup, payment, and pricing se…

69884e6

…ctions

Remove obsolete billing-related HTML files and update _routes.yml to …

e96e33c

…reflect the changes

Add new articles on Expensify plans, pricing, and billing to _routes.…

5939ceb

…yml and create corresponding markdown files

Update titles in _routes.yml for consistency and formatting

5bcb13c

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[No QA] Helpsite consolidateV2 #81045

[No QA] Helpsite consolidateV2 #81045

Uh oh!

stephanieelliott commented Jan 30, 2026 •

edited

Loading

Uh oh!

melvin-bot bot commented Jan 30, 2026

Uh oh!

melvin-bot bot commented Jan 30, 2026

Uh oh!

github-actions bot Jan 30, 2026

Uh oh!

github-actions bot Jan 30, 2026

Uh oh!

github-actions bot Jan 30, 2026

Uh oh!

github-actions bot commented Jan 30, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

chatgpt-codex-connector bot Jan 30, 2026

Uh oh!

OSBotify commented Jan 30, 2026 •

edited

Loading

Uh oh!

codecov bot commented Jan 30, 2026 •

edited by github-actions bot

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

[No QA] Helpsite consolidateV2 #81045

Are you sure you want to change the base?

[No QA] Helpsite consolidateV2 #81045

Uh oh!

Conversation

stephanieelliott commented Jan 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Jan 30, 2026

Concierge reviewer checklist:

Uh oh!

melvin-bot bot commented Jan 30, 2026

Uh oh!

github-actions bot Jan 30, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Jan 30, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Jan 30, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Jan 30, 2026

HelpDot Documentation Review

Overall Assessment

Scores Summary

Key Findings - Critical Issues

Recommendations Priority 1 - Blocking

Files Reviewed

Final Recommendation

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector bot Jan 30, 2026

Choose a reason for hiding this comment

Uh oh!

OSBotify commented Jan 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

codecov bot commented Jan 30, 2026 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

stephanieelliott commented Jan 30, 2026 •

edited

Loading

OSBotify commented Jan 30, 2026 •

edited

Loading

codecov bot commented Jan 30, 2026 •

edited by github-actions bot

Loading